Skip to content

Conversation

@johnjenkins
Copy link
Contributor

@johnjenkins johnjenkins commented Oct 17, 2025

What is the current behavior?

GitHub Issue Number: #6425

What is the new behavior?

Fixes #6425

Temporary fix until a) Typescript properly type autocorrect b) ionic loosen it's autocorrect type

Documentation

Does this introduce a breaking change?

  • Yes
  • No

Testing

Other information

@johnjenkins johnjenkins requested a review from a team as a code owner October 17, 2025 18:27
@johnjenkins johnjenkins changed the title fix(types): temporary fix - make autocorrect 'any' fix(types): temporary autocorrect fix Oct 17, 2025
@johnjenkins johnjenkins merged commit 7044550 into main Oct 17, 2025
69 checks passed
@johnjenkins johnjenkins deleted the fix-autocorrect-type branch October 17, 2025 19:17
@Tallyb
Copy link
Contributor

Tallyb commented Oct 20, 2025

The problem with this fix is that if we have autocorrect property it blocks it. why not define autocorrect as boolean?

@johnjenkins
Copy link
Contributor Author

yeah - this was just a temporary thing.
The main issue at present is compat with ionic (they have some components with an autocorrect property).
I'm working with the ionic team to get around it (shifting the workaround into ionic, out of Stencil).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: Breaking Type Incompatibility: HTMLStencilElement.autocorrect ('on' | 'off') vs HTMLElement.autocorrect (boolean)

3 participants